SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 59867: A segmentation violation occurs when running a stored process fails that executes the %apm_request_init macro

DetailsHotfixAboutRate It

A segmentation violation error and stored process failure might occur while processing the %apm_request_init macro using the SAS® Stored Process Server, pooled workspace server, or standard workspace server. The %apm_request_init macro is part of the EMI framework that can be enabled for SAS® Environment Manager monitoring. The segmentation violation occurs when the logon ID for the connecting user exceeds approximately 40 characters in length. The following traceback appears in the server log file:

 +%apm_request_init;
 
ERROR:  An exception has been encountered.
Please contact technical support and provide them with the following traceback information:
 
The SAS task name is [STPX_LP ]
Segmentation Violation
Traceback of the Exception:
/sas/install/SASFoundation/9.4/sasexe/sas(+0x15aa6e) [0x7f8997290a6e]
/sas/install/SASFoundation/9.4/sasexe/sas(+0x4cb0b) [0x7f8997182b0b]
/sas/install/SASFoundation/9.4/sasexe/tkmk.so(bkt_signal_handler+0x144) [0x7f8995b4d3c4]
/lib64/libpthread.so.0(+0xf7e0) [0x7f8996d057e0]
/sas/install/SASFoundation/9.4/sasexe/tkmk.so(skm_unlink+0x21) [0x7f8995b608e1]
/sas/install/SASFoundation/9.4/sasexe/tkmk.so(skmMemAlloc+0x19e) [0x7f8995b5e54e]
/sas/install/SASFoundation/9.4/sasexe/tk4aarm4.so(arm4createSubbuffer+0x9b5) [0x7f8983035705]
/sas/install/SASFoundation/9.4/sasexe/tk4aarm4.so(arm4start+0x24bd) [0x7f8983020b3d]
/sas/install/SASFoundation/9.4/sasexe/tk4aarm4.so(+0x5a2b) [0x7f8983014a2b]
/sas/install/SASFoundation/9.4/sasexe/tkl4sas.so(+0x31d55) [0x7f898d98ad55]
/sas/install/SASFoundation/9.4/sasexe/tkl4sas.so(Log4SASCallAppenders+0x1c7) [0x7f898d964cd7]
/sas/install/SASFoundation/9.4/sasexe/tkl4sas.so(Log4SASSpewEvent+0xba) [0x7f898d964a8a]
/sas/install/SASFoundation/9.4/sasexe/tkl4sas.so(LoggerLogEventEDC+0x17d) [0x7f898d9854bd]
/sas/install/SASFoundation/9.4/sasexe/tkl4sas.so(LoggerLogEvent+0x3a) [0x7f898d9847aa]
/sas/install/SASFoundation/9.4/sasexe/tkarm.so(tka_start+0xc53) [0x7f898c4a80b3]
/sas/install/SASFoundation/9.4/sasexe/uwutrans(txnstrt+0x276) [0x7f892d526736]
/sas/install/SASFoundation/9.4/sasexe/sasxfnc(yfxfn+0x1ff) [0x7f895614a69f]
/sas/install/SASFoundation/9.4/dbcs/sasexe/sasxmac(yjsysf+0xe74) [0x7f8960c68534]
/sas/install/SASFoundation/9.4/dbcs/sasexe/sasxmac(yjoch+0x2c55) [0x7f8960c79635]
/sas/install/SASFoundation/9.4/dbcs/sasexe/sasxshel(ytscan+0x2543) [0x7f8983b7b6e3]
/sas/install/SASFoundation/9.4/dbcs/sasexe/sasxshel(yjdelta+0x33) [0x7f8983b61183]
/sas/install/SASFoundation/9.4/dbcs/sasexe/sasxmac(+0x24530) [0x7f8960c65530]
/sas/install/SASFoundation/9.4/dbcs/sasexe/sasxmac(yjintrp+0x2180) [0x7f8960c61380]
/sas/install/SASFoundation/9.4/dbcs/sasexe/sasxshel(+0x50a82) [0x7f8983b7ca82]
ERROR: Generic critical error.

Currently the only circumvention is to disable the EMI framework for the stored process server, pooled workspace server, and workspace server:

  • On the service architecture framework machine, change to the SAS-configuration-directory/Lev1/Web/SASEnvironmentManager/emi-framework/bin directory.
  • From a command line, issue the command ./emi_init.sh --disable APM (UNIX) or emi_init.bat --disable APM (Windows) to disable only the APM ETL. Issue the command ./emi_init.sh --disable ALL (UNIX) or emi_init.bat --disable ALL (Windows) if you want to disable the APM, ACM, and solution kit ETLs. Syntax for the emi_init.sh script can be found here.

Click the Hot Fix tab in this note to access the hot fix for this issue.



Operating System and Release Information

Product FamilyProductSystemSAS Release
ReportedFixed*
SAS SystemBase SASz/OS9.3 TS1M29.4 TS1M5
z/OS 64-bit9.3 TS1M29.4 TS1M5
Microsoft® Windows® for x649.3 TS1M29.4 TS1M5
Microsoft Windows 8 Enterprise 32-bit9.3 TS1M29.4 TS1M5
Microsoft Windows 8 Enterprise x649.3 TS1M29.4 TS1M5
Microsoft Windows 8 Pro 32-bit9.3 TS1M29.4 TS1M5
Microsoft Windows 8 Pro x649.3 TS1M29.4 TS1M5
Microsoft Windows 8.1 Enterprise 32-bit9.3 TS1M29.4 TS1M5
Microsoft Windows 8.1 Enterprise x649.3 TS1M29.4 TS1M5
Microsoft Windows 8.1 Pro 32-bit9.3 TS1M29.4 TS1M5
Microsoft Windows 8.1 Pro x649.3 TS1M29.4 TS1M5
Microsoft Windows Server 2003 Datacenter Edition9.3 TS1M2
Microsoft Windows Server 2003 Enterprise Edition9.3 TS1M2
Microsoft Windows Server 2003 Standard Edition9.3 TS1M2
Microsoft Windows Server 2003 for x649.3 TS1M2
Microsoft Windows Server 20089.3 TS1M2
Microsoft Windows Server 2008 R29.3 TS1M2
Microsoft Windows Server 2008 for x649.3 TS1M2
Microsoft Windows Server 2012 Datacenter9.3 TS1M29.4 TS1M5
Microsoft Windows Server 2012 R2 Datacenter9.3 TS1M29.4 TS1M5
Microsoft Windows Server 2012 R2 Std9.3 TS1M29.4 TS1M5
Microsoft Windows Server 2012 Std9.3 TS1M29.4 TS1M5
Microsoft Windows XP Professional9.3 TS1M2
Windows 7 Enterprise 32 bit9.3 TS1M29.4 TS1M5
Windows 7 Enterprise x649.3 TS1M29.4 TS1M5
Windows 7 Home Premium 32 bit9.3 TS1M29.4 TS1M5
Windows 7 Home Premium x649.3 TS1M29.4 TS1M5
Windows 7 Professional 32 bit9.3 TS1M29.4 TS1M5
Windows 7 Professional x649.3 TS1M29.4 TS1M5
Windows 7 Ultimate 32 bit9.3 TS1M29.4 TS1M5
Windows 7 Ultimate x649.3 TS1M29.4 TS1M5
Windows Vista9.3 TS1M2
Windows Vista for x649.3 TS1M2
64-bit Enabled AIX9.3 TS1M29.4 TS1M5
64-bit Enabled HP-UX9.3 TS1M29.4 TS1M5
64-bit Enabled Solaris9.3 TS1M29.4 TS1M5
HP-UX IPF9.3 TS1M29.4 TS1M5
Linux9.3 TS1M29.4 TS1M5
Linux for x649.3 TS1M29.4 TS1M5
Solaris for x649.3 TS1M29.4 TS1M5
Microsoft Windows 109.4 TS1M39.4 TS1M5
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.